Snooze Transaction
AutomatR.OrchestratorActivities.SnoozeTransaction
The "Snooze Transaction" activity in AutomatR OrchestratorActivities temporarily suspends a transaction in Orchestrator, delaying its processing until a specified date. This activity is useful for managing the timing of transaction execution and is particularly valuable for scenarios where a transaction needs to be postponed until a later time.
Properties
| Name | Description |
|---|---|
| Input | |
| Transaction ID | Specifies the ID of the transaction to be snoozed. String variables containing the transaction ID. |
| Postpone Until | Specifies the date after which the queue item may be processed. DateTime variables containing the postponed date and time. |
| High Priority | When selected, sets the queue item in high priority. |
| Custom Data | Enter custom data in dictionary format to associate additional information with the transaction. |
| Replace Custom Data | Select True or False to indicate whether to replace existing custom data with the provided data. If True, existing custom data is replaced; if False, new data is appended. |
| Custom Status Key | Specifies a custom status key to be set for the transaction. |
| Misc | |
| Display Name | Provides a customizable name for the activity displayed in the workflow. The display name enhances clarity and organization within the automation project. String variable or argument containing the desired display name. |
| Optional | |
| Delay | Specifies the amount of time (in seconds) to wait before executing the "Snooze Transaction" activity. Useful for handling synchronization issues. Integer variables containing the delay duration. Ex.: If the time is 1000 milliseconds or 1 sec, i.e., 1. |
| Output | |
| Status | Outputs the result of the "Snooze Transaction" operation, indicating whether the transaction was snoozed successfully or encountered errors. Boolean variables to store the operation result. |
How to use:
- Drag and drop the "Snooze Transaction" activity onto the workflow.
- Configure the properties by specifying the transaction ID and the date after which the transaction should be processed.
- Optionally, configure additional parameters such as custom data, custom status key, and high priority.
- Execute the workflow to temporarily suspend the specified transaction in Orchestrator.
Example: Consider an example where the "Snooze Transaction" activity is used to postpone the processing of a transaction:
Snooze Transaction:
Transaction ID: "123456"
Postpone Until: "2023-01-01T12:00:00"
Custom Data: { "Key1": "Value1", "Key2": "Value2" }
Replace Custom Data: True
Custom Status Key: "CustomKey"
High Priority: True
Status: isTransactionSnoozedSuccessfully
In this example, the activity postpones the processing of the transaction with ID "123456" until January 1, 2023, and associates custom data, a custom status key, and sets high priority. The result of the operation (success or failure) is stored in the Boolean variable "isTransactionSnoozedSuccessfully" for further handling in the workflow.